Location-based services platform

ABSTRACT

A platform for providing location-based services is disclosed. A location data collection client running on a mobile device periodically obtains data allowing determination of the geographic location of the mobile device (e.g., GPS, cell tower, or WiFi data) and transmits that data and mobile device-specific information to a location-based services (LBS) platform server. The LBS platform server determines geographic location of the mobile device from the received data. For example, the LBS platform server accesses databases associating latitude and longitude coordinates with cell tower data or WiFi data and updates mobile device location to maintain current location information for the mobile device, which can be used as a proxy for the location of a mobile device user. The LBS platform server further includes a set of APIs allowing third-party services providers to access to the location data.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.12/434,508, filed May 1, 2009, which claims the benefit of U.S.Provisional Application No. 61/050,180, filed May 2, 2008, both of whichare incorporated by reference herein in their entireties.

BACKGROUND

This invention relates generally to location-based services, and moreparticularly to a platform providing location data to third-partyservice providers.

Location-based services (LBS) make use of the geographical location of amobile device, such as a mobile phone, to provide the mobile device withdata relevant to the mobile device's geographical location. ProvidingLBS allows a third-party service provider or wireless service operatorto deliver customized content to mobile devices. Data supplied via LBSmay identify an entity, such as a person, business or other object thatis near the geographic location of the mobile device, providing a mobiledevice user with data about the surrounding area. Additionally, LBScould allow movement of a mobile device over time to be tracked ortransmission of information, such as notifications, alerts or coupons,to the mobile device when it is geographically near a specifiedlocation. The tracking of a device is generally used as a proxy to tracka person or asset.

The location data determining mobile device geographic location may beobtained using various methods and maintained in different formats.Because of this, different wireless operators and third-party serviceproviders differently calculate and maintain mobile device geographiclocation data. Additionally, privacy considerations regarding mobiledevice geographic location data may be affected by contracts,regulations or policies specific to different wireless carriers.Accordingly, mobile device geographic location data is generallyseparately calculated and maintained by different wireless carriers,requiring third-party service providers offering LBS applications todevelop separate applications specific to different wireless carriers.This need to separately develop and maintain wireless carrier-specificapplications hinders the development and adoption of LBS applicationsoffered by third-party providers. Further because wireless operatorsgenerally do not provide location to Providers, Providers generally needto build location based applications in the form of softwaredownloadable to the mobile device or through proprietary hardware.Providers must generally choose between using Location Data provided bywireless operators or Location Data extracted from the mobile device.

SUMMARY

Embodiments of the invention relate to a platform for providinglocation-based services. A location data collection client running on amobile device periodically obtains data allowing determination of thegeographic location of the mobile device (e.g., GPS, cell tower, or WiFidata) and transmits that data and mobile device-specific information toa location-based services (LBS) platform server. The LBS platform serverdetermines geographic location of the mobile device from the receiveddata. For example the LBS platform server accesses databases relatinggeographic locations to cell tower data or WiFi data (e.g., by the MACaddresses of access points) and identifies latitude and longitudecoordinates associated with the cell tower data or WiFi data. In anembodiment, the LBS platform server may also receive data allowingdetermination of the geographic location of the mobile device fromadditional sources, such as a hardware device or a wireless operator.The LBS platform server updates mobile device location to maintaincurrent location information for the mobile device, which can be used asa proxy for the location of a mobile device user. The LBS platformserver further includes a set of APIs allowing third-party serviceproviders to access to the location data. Various applications areenabled by this platform, including pull models where third-partyservices poll the location data and push models where the server sendsthe location data according to predefined algorithms.

For example, an API stored on the LBS platform server allows athird-party service provider to retrieve a mobile device location fromthe LBS platform server in response to a data request or to determineother mobile devices or locations within a certain radius of theretrieved mobile device location. Another API stored on the LBS platformserver allows the LBS platform server to push mobile device location toa third-party service provider when mobile device movement meetsparameters specified by the third-party service provider or when themobile device location is within a specified radius of another mobiledevice or specified location. In an embodiment, a third-party serviceprovider may provide customized location logic to specify when mobiledevice location is transmitted from the LBS platform server to thethird-party service provider. Additionally, the stored APIs may alsoinclude presentation or formatting layer, to simplify distribution ofcontent or other data from the third-party content provider.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a high-level block diagram of a system environment for aplatform providing location-based services invention, in accordance withan embodiment of the invention.

FIG. 2 is a block diagram of a mobile device in accordance with anembodiment of the invention.

FIG. 3 is a diagram of a location-based platform server in accordancewith an embodiment of the invention.

FIG. 4 is an event diagram of a third-party service provider generatinglocation-based content in accordance with an embodiment of theinvention.

FIG. 5 is a flow chart of a method for providing location informationabout a mobile device in accordance with an embodiment of the invention.

FIG. 6 is a flow chart of a method for updating data describing thegeographic location of a mobile device in accordance with an embodimentof the invention.

The Figures depict various embodiments of the present invention forpurposes of illustration only. One skilled in the art will readilyrecognize from the following discussion that alternative embodiments ofthe structures and methods illustrated herein may be employed withoutdeparting from the principles of the invention described herein.

DETAILED DESCRIPTION Location-Based Services Platform Architecture

Embodiments of the invention may be implemented using variousarchitectures, such as the example architecture illustrated in FIG. 1.In this embodiment, location-based services (LBS) platform comprises oneor more mobile devices 110, a network 120, a location-based platform(LBS) server 130 and a third-party service provider 140. The LBSplatform may also include a location database 135. While FIG. 1 depictsa single third-party service provider 140, in other embodiments multiplethird-party service provides 140 are included in the LBS platform.

The one or more mobile devices 110 include onboard processingcapabilities and data communication capabilities, such as Bluetooth,WiFi, RF, infrared and ultrasonic sound, as well as input/outputfunctionalities. For example, a mobile device 110 comprises a mobilephone, a personal digital assistant, a smart phone, a navigation deviceor a laptop computer. However, a mobile device 110 may be any devicecapable of processing data and communicating data that can be movedbetween geographic locations, such as a watch or a car. The mobiledevice 110 also receives input from a user and presents output to theuser. A mobile device 110 is described in more detail below inconjunction with FIG. 2. As further described in conjunction with FIG.2, the one or more mobile devices 110 include a location data collectionclient 225 which extracts data from the mobile device. The extracteddata may comprise global positioning system (GPS) data describing thelatitude and longitude of the mobile device 110, cell-tower dataidentifying one or more cell towers that are geographically nearest tothe mobile device 110 or data identifying one or more wireless accesspoints geographically nearest to the mobile device 110. In oneconfiguration the location data collection client 225 extracts data froma location API executing on the mobile device 110 obtaining GPS dataand/or additional location data from the mobile device 110. In anembodiment, the location data collection client 225 also extracts dataspecific to the mobile device 110, such as a device type, a timestampwhen data was extracted or an International Mobile Equipment Identity(IMEI) number or other product key, such as IMEA number.

The network 120, which may comprise any combination of local area and/orwide area networks using wireless communication systems, communicatesdata between the one or more mobile devices 110, the LBS platform server130 and/or the third-party service provider 140. In an embodiment, thenetwork 120 uses a combination of wireless and wired communicationsystems to communicate data. To communicate data between the one or moremobile devices 110, the LBS platform server 130 and/or the third-partyservice provider 140, the network 120 may employ a secure web serviceusing Hypertext Transfer Protocol (HTTP) and/or Hypertext TransferProtocol over Secure Socket Layer (HTTPS). Alternatively, the network120 may use the Transmission Control Protocol (TCP) for datacommunication.

The LBS platform server 130 communicates with the one or more mobiledevices 110 and/or the third-party service provider 140 via the network120. The LBS platform server 120 receives data from a location datacollection client 225 running on a mobile device 110 and processes thereceived data to determine the geographic location of the mobile device110 or extract data associated with the mobile device 110, such asdevice type or timestamp associated with data extraction. In anembodiment, the LBS platform server 130 communicates with a locationdatabase 135 which determines mobile device 110 geographic location froma location data collection client 225.

For example, the location data collection client 225 extracts dataidentifying one or more cell towers geographically closest to the mobiledevice 110. The data identifying the one or more cell towers is receivedby the LBS platform server 130, which communicates the data identifyingthe one or more cell towers to the location database 135 includinglatitude and longitude coordinates associated with various cell towers.The latitude and longitude coordinates of the one or more cell towersidentified by the location data collection client 225 are transmittedfrom the location database 135 to the LBS platform server 130 toidentify the current position of the mobile device 110. In anembodiment, the LBS platform server 130 or the location database 135 mayuse a reverse geo-coder to convert the latitude and longitudecoordinates of the identified one or more cell towers as a streetaddress, a city, a zip code or a country.

As another example, the location data collection client 225 extractsdata identifying one or more wireless access point geographicallyclosest to the mobile device 110. The data identifying the cell towersis received by the LBS platform server 130, which communicates the dataidentifying the one or more wireless access points to the locationdatabase 135 including latitude and longitude coordinates associatedwith various wireless access points. The latitude and longitudecoordinates of the one or more wireless access points identified by thelocation data collection client 225 are transmitted from the locationdatabase 135 to the LBS platform server 130 to identify the currentposition of the mobile device 110. In an embodiment, the LBS platformserver 130 or the location database 135 may use a reverse geo-coder toconvert the latitude and longitude coordinates of the identified one ormore wireless access points as a street address, a city, a zip code or acountry.

Although shown in FIG. 1 as separate from the LBS platform server 130,in other embodiments, the location database 135 is included in the LBSplatform server 130 to allow local determination of mobile device 110geographic location. For example, the LBS platform server 130 includesone or more databases associating latitude and longitude coordinateswith various wireless access points or associating latitude andlongitude coordinates with various cell towers.

As further described below in conjunction with FIG. 3, the LBS platformserver 130 include one or more application programming interfaces (APIs)to allow integration of applications with the LBS platform server 130.The one or more APIs allow a third-party service provider 140 to accessgeographic locations of one or more mobile devices 110 from the LBSplatform server 130, enabling the third-party service provider 140 toprovide a mobile device 110 with content customized according to thegeographic position of the mobile device 110. Privacy settings stored bythe LBS platform server 130 may be used to regulate data about a mobiledevice 110 provided to the third-party service provider 140 by an API.

FIG. 2 illustrates an embodiment of a mobile device 110 for use in alocation-based service (LBS) platform, such as the embodiments describedabove. In the embodiment shown in FIG. 2, the mobile device 110comprises a processor 210, a data store 220, an input device 230, anoutput device 240, a power supply 250, a communication module 260 and aGlobal Positioning System (GPS) module 270. It should be understood,however, that not all of the above components are required for themobile device 110, and this is not an exhaustive list of components forall embodiments of the mobile device 110 or of all possible variationsof the above components. A mobile device 110 may have any combination offewer than all of the capabilities and components described herein.

The processor 210, data store 220, and the power supply 250, such as abattery or any other suitable power source enable the mobile device 110to perform computing functionalities. The processor 210 is coupled tothe input device 230 and the output device 240 enabling applicationsrunning on the smart pen 100 to use these devices. In one embodiment,the data store 220 comprises a small amount of random access memory(RAM) and a larger amount of flash or other persistent memory, allowingapplications, such as the location data collection client 225, to bestored and executed by the mobile device 110. This allows the locationdata collection client 225 to extract data from the mobile device 110describing geographic location of the mobile device. The mobile devicealso executes an operating system or other software supporting one ormore input modalities, for receiving input from the input device 230and/or one or more output modalities presenting data via the outputdevice 240, such as audio playback or display of visual data.

The output device 240 may comprise any suitable display system forproviding visual feedback, such as an organic light emitting diode(OLED) display. The output device 240 may also include a speaker orother audio playback device to provide auditory feedback. For example,the output device 240 may communicate audio feedback (e.g., prompts,commands, and system status) according to an application running onmobile device 110 using the speaker and also display word phrases,static or dynamic images, or prompts as directed by the applicationusing the display. The input device 240 comprises any suitable devicefor receiving input from a user, such as a keyboard, touch-sensitivedisplay or gesture capture system.

The communication module 260 comprises a wireless communication circuitallowing wireless communication with the network 120 (e.g., viaBluetooth, WiFi, RF, infrared, or ultrasonic). For example, thecommunication module 260 identifies and communicates with one or morewireless access points using WiFi or identifies and communicates withone or more cell towers using RF. In an embodiment, the communicationmodule 260 also includes a jack for receiving a data cable (e.g.,Mini-USB or Micro-USB). The GPS module 270 determines geographiclocation of the mobile device 110 by timing signals received from GPSsatellites to calculate distance from the GPS module 270 and each GPSsatellites.

The location data collection client 225 extracts data from the GPSmodule 270 identifying the geographic location of the GPS module 270 toidentify the location of the mobile device 110. Additionally, thelocation data collection client 225 extracts data from the communicationmodule 260 identifying one or more cell towers and/or wireless accesspoints geographically near the mobile device 260. Data extracted by thelocation data collection client 225 is transmitted via the communicationmodule 260 to a LBS platform server 130 at predefined intervals. Forexample, at five-minute intervals, the location data collection client225 transmits data to the LBS platform server 130 using thecommunication module 260. In an embodiment, the frequency at which thelocation data collection client 225 transmits data to the LBS platformserver is increased or decreased based on different parameters, such asamount of movement by the mobile device 110, network usage, a specifiedmaximum delay interval or use of mobile device 110 hardware. Forexample, if the power supply 250 operates at less than half of fullcapacity, the frequency of data transmission by the location datacollection client 225 is decreased. FIG. 6, further described below,illustrates an example method for modifying the frequency of datatransmission by the location data collection client 225 responsive topower supply 250 life.

FIG. 3 illustrates a block diagram of an embodiment of a LBS platformserver 130 for use in a location-based service (LBS) platform, such asthe embodiments described above. In the embodiment shown in FIG. 3, theLBS platform server 130 comprises a device identifier store 305, aprovider identifier store 310, a device-provider association table 320,a third-party service server 330, an API generator 340, an internallocation database 350 and a location calculator 360. It should beunderstood, however, that not all of the above components are requiredfor the LBS platform server 130, and this is not an exhaustive list ofcomponents for all embodiments of the LBS platform server 130 or of allpossible variations of the above components. A LBS platform server 130may have any combination of fewer than all of the capabilities andcomponents described herein.

The device identifier store 305 is a persistent storage device includingone or more device identifiers. As used herein, a “device identifier”refers to a combination of a client identifier associated with alocation data collection client 225 running on a mobile device 110 and amobile device identifier, such as a serial number, IDMA number or otheridentifier associated with the mobile device. A device identifier isassociated with a mobile device 110 running the location data collectionclient 225 to uniquely identify the mobile device 110 by including aclient identifier associated with the location data collection client225 and a mobile device identifier associated with the mobile device110. For example, the client identifier is received by the mobile device110 when the location data collection client 225 is installed, or whenthe location data collection client 225 is initially operated. Thisclient identifier is combined with a mobile device identifier retrievedfrom the mobile device 110 by the location data collection client, andthe client identifier and mobile device identifier are combined togenerate the device identifier. In one embodiment, the device identifierstore 305 restricts access to the device identifiers received from oneor more mobile devices 110 running the location data collection client225 to prevent entities other than the LBS platform server 130 fromaccessing the device identifiers. For example, third-party serviceproviders 140 are prevented from accessing the device identifier store305 to maintain the privacy of the identified mobile devices 110.

Similarly, the provider identifier store 310 is a persistent storagedevice including one or more provider identifiers that uniquely identifythird-party service providers 140. When a third-party service provider140 desires to provide an application or other content at leastpartially dependent on the geographic location of a mobile device 110,the provider identifier store 310 generates and stores a provideridentifier uniquely identifying the third-party service provider 140.The generated provider identifier is also transmitted to the third-partyservice provider 140 and used to later request data from the LBSplatform server 130. Maintaining separate provider identifiers anddevice identifiers allows the LBS platform server 130 to preserve theprivacy of different mobile devices 110 while allowing a third-partyservice provider 140 to receive at least a subset of data associatedwith mobile devices 110.

Additionally, the third-party service provider 140 may also locallystore and maintain a user identifier associated with different users ofmobile devices 110 that receive content from the third-party serviceprovider 140. While the device identifier stored by the LBS server 130in the device identifier store 305 uniquely identifies a mobile device140, the third-party service provider 140 locally maintains useridentifiers describing different users who receive content from thethird-party service provider 140. Because the third-party serviceprovider 140 identifies individual users receiving content while the LBSplatform server 130 identifies individual mobile devices 110 whoselocation is tracked, the third-party service provider 140 cannot use thedevice to obtain location data from the LBS server 130.

To communicate device location data to a third-party service provider140, the LBS server includes a device-provider association table 320mapping mobile device identifiers to provider identifiers. In anembodiment, the device-provider association table 320 also uses datafrom the third-party service provider 140, such as user identifier orother user data, to identify a mobile device 110 associated with a userof the third-party service provider 140. For example, thedevice-provider association table 320 associates a device identifierwith a combination of a provider identifier and a user identifier fromthe third-party service provider 140. This enables the device-providerassociation table 320 to map a mobile device 110 to a particular user ofthe third-party service provider 140. In an embodiment, thedevice-provider association table 320 comprises a lookup tableassociating a device identifier with a provider identifier orassociating a device identifier with a combination of provideridentifier and user-specific data, such as a login, key, email addressor other data used by the third-party service provider 140 to uniquelyidentify users. Additionally, the device-provider association table 320may include permissions associated with different device identifierslimiting the data associated with a mobile device 110 that may becommunicated to a third-party service provider 140.

To simplify exchange of mobile device 110 location data with athird-party service provider 140, the third-party service server 330includes predefined APIs for providing subsets of data to thethird-party service provider 140. In one embodiment, the third-partyservice server 330 includes a push API and a pull API. If the push APIis used, the LBS platform server 130 transmits updated locationinformation to a third-party service provider 140 when new geographiclocation data is received from a location data collection client 225running on a mobile device 110. This allows the LBS platform server 130to push updated location data to the third-party service provider 140 asa mobile device 110 changes location. In an embodiment, the locationdata communicated to the third-party service provider 140 is regulatedby device-specific settings, such as permissions associated with adevice identifier included in the device-provider association table 320.

For example, a permission associated with a device identifier specifieswhether the location of the corresponding mobile device 110 iscommunicated to the third-party service provider 140 as latitude andlongitude coordinates, street names, city name, county name or countryname. Permissions associated with a device identifier also allow a userof the mobile device 110 to identify third-party service providers 140are able to receive location information associated with the mobiledevice 140, allowing the user to regulate access to the locationinformation. Additionally, a permission allows a user of the mobiledevice 110 to identify the granularity of the location informationcommunicated to a third-party service provider 140. For example, apermission allows a third-party service provider 140 to receive latitudeand longitude coordinates associated with the mobile device 110, whileanother permission allows a different third-party service provider 140to merely receive data indicating the city where the mobile device 110is located. An additional permission may allow a user to regulate thelength of time that location data is communicated to a third-partyservice provider 140.

By pushing updated location data to a third-party service provider 140,an API allows the third-party service provider 140 to automaticallyprovide content or applications when a mobile device 110 is near aspecified location or other mobile device 110. In an embodiment, thepush API may receive parameters from a third-party service provider 140to transmit geographic location to the third-party service provider 140when the parameters are satisfied, reducing the amount of communicationbetween the LBS platform server 130 and the third-party service provider140. For example, the push API communicates an update or notificationmessage to the third-party service provider 140 when the mobile device110 is within a predefined radius of an entity, such as another mobiledevice 110 or a specific location. As another example, the push APIcommunicates a notification message to a third-party service provider140 when the location of a mobile device 110 exceeds a threshold or whenthe location of the mobile device 110 changes at more than a predefinedrate.

The pull API transmits the geographic location of a mobile device 110responsive to the LBS platform server 130 receiving a request from athird-party service provider 140. The third-party service server 330allows the third-party service provider 140 to determine the location ofa mobile device 110 and provide content to the mobile device 110customized to the geographic location of the mobile device 110. Forexample, the pull API allows a third-party service provider 140 toretrieve latitude and longitude coordinates of a mobile device 110, themethod used to calculated the latitude and longitude of the mobiledevice 110 (e.g., GPS data, cell tower identification, wireless accesspoint identification, etc.), a timestamp specifying when the latitudeand longitude coordinates were calculated, and/or geocoded data, such asa street address, associated with the latitude and longitude coordinatesfrom the LBS platform server. As another example, the pull API allows athird-party service provider 140 to retrieve data from the LBS platformserver 130 describing locations the mobile device 110 had previouslyaccessed within a specified time interval, allowing the third-partyservice provider 110 to generate a history of mobile device 110locations. As another example, the pull API allows the third-partyservice provider 140 to determine the current location of a mobiledevice 110 and identify locations or other mobile devices 110 within aspecified radius of the current location of the mobile device 110.

In addition to the third-party service server 330, the LBS platformserver includes an API generator 340 which allows a third-party serviceprovider 140 to generate customized rules or parameters for receivinglocation data associated with a mobile device 110. While the Third-partyservice server 330 includes predefined APIs for performing predefinedfunctions and returning predefined data, the API generator 340 allows athird-party service provider 140 to customize when location data iscommunicated from the LBS platform server 130 to the third-party serviceprovider 140. Additionally, the API generator 340 allows a third-partyservice provider 140 to customize the format in which data iscommunicated to the third-party service provider 140. For example, theAPI generator 340 specifies that a street address describing thelocation of the third-party service provider 140 is transmitted to thethird-party service provider 140.

The internal location database 350 comprises a persistent storagedevice, or combination of a persistent storage device and anon-persistent storage device, storing data received from location datacollection clients 225 running on mobile devices 110 and stores datadescribing geographic location of the mobile devices 110. In oneembodiment, the internal location database 350 stores latitude andlongitude coordinates extracted from a GPS module 270 of a mobile device110. Data in the internal location database 350 describing geographiclocation of a mobile device 110 is associated with a device identifierfrom the device identifier store 350 to create a pairing of deviceidentifier and geographic location of the mobile device 110 associatedwith the device identifier.

However, because the location data collection client 225 extractsdifferent types of data from a mobile device 110 for determininggeographic position, data from the location data collection client 225may be converted into latitude and longitude coordinates of the mobiledevice 110. For example, the location data collection client 225extracts data identifying a wireless access point or cell towergeographically near the mobile device 110. The location calculator 360converts received data into latitude and longitude coordinates using avariety of methods. For example, the location calculator 360 includesand retrieves the latitude and longitude coordinates of the cell toweror wireless access point received from the mobile device 110. In oneembodiment, the location calculator 360 locally stores latitude andlongitude coordinates associated with cell towers or wireless accesspoints. Alternatively, the location calculator 360 transmits data to anexternal location database 135 which determines latitude and longitudecoordinates and transmits the latitude and longitude coordinates to thelocation calculator 360.

Providing Location Based Services

FIG. 4 shows an event diagram of an example process for a third-partyservice provider 140 to generating location-based content using datafrom a location based services (LBS) platform server 130. The actionsdescribed in FIG. 4 can be implemented by various computer systemsexecuting instructions that cause the described actions. Those of skillin the art will recognize that one or more of the actions may beimplemented in embodiments of hardware and/or software or combinationsthereof. For example, instructions for performing the described actionsare embodied or stored within a computer readable storage medium. Otherembodiments can include different and/or additional steps than the onesdescribed here.

When the location data collection client 225 is installed on a mobiledevice 110 or when the location data collection client 225 is used forthe first time on a mobile device 110, a client identifier is generated405 by server and received 405 by the location data collection client225 running on the mobile device 110. The client identifier uniquelyidentifies the location data collection client 225 running on the mobiledevice 110. The location collection client 225 then extracts a mobiledevice identifier from the mobile device 110, such as an electronicserial number or international mobile equipment identity number. Thelocation collection client 225 then combines the mobile deviceidentifier and the client identifier to generate a device identifierwhich is transmitted 415 from the mobile device 110 to the LBS platformserver 130, where it is stored 425 in the device identifier store 305.Storing 425 the device identifier allows the LBS platform server 130 tosubsequently identify the mobile device 110 running the location datacollection client 225.

When a third-party service provider 140 requests access to the LBSplatform server 130, a publisher identifier uniquely identifying thethird-party service provider 140 is generated by the LBS platform server130, stored in the publisher identifier store 310 and transmitted 415 tothe third-party service provider 140. The third-party service provider140 stores 420 the publisher identifier for later access to the LBSplatform server 140. This allows the LBS platform server 130 to locallystore device identifiers and publisher identifiers which uniquelyidentify mobile devices 110 and third-party service providers 140,respectively, communicating with the LBS platform server 130.

After transmitting 415 the device identifier, the location datacollection client 225 extracts 435 data from the mobile device 110. Forexample, the location data collection client extracts 435 latitude andlongitude coordinates from a GPS module 270 of the mobile device 110,extracts 435 data identifying a cell tower geographically near themobile device 110 or extracts 435 data identifying a wireless accesspoint geographically near the mobile device 110. However, these aremerely examples of data extracted 435 by the location data collectionclient 225, and any data suitable for determining a location associatedwith the mobile device 110 may be extracted 435. Additionally, thelocation data collection client 225 may also extract 435 data associatedwith the mobile device 110, such as the device type, a timestampidentifying the time at which data was extracted or other data.

The extracted data is transmitted 440 to the LBS platform server 130which uses the extracted data to determine 445 the location of themobile device 110 and associated the determined location with the storeddevice identifier. For example, the LBS platform server 130 uses alocation calculator 360 to determine the latitude and longitudecoordinates of a cell tower or wireless access point identified by theextracted data. In one embodiment, the extracted data is transmitted 440to the LBS platform server at a predetermined frequency, such as everyfive minutes. Alternatively, the location data collection client 225modifies the frequency at which the extracted data is transmitted 440based on characteristics of the mobile device 110, such as network usageor power supply 250 life. An example of modification of the transmissionfrequency is further described below in conjunction with FIG. 6.

The LBS platform server 130 then stores the determined location of themobile device 110 in the internal location database 350, whichassociates the determined location with the device identifier. Thisallows the LBS platform server 130 to locally maintain record of thelocation associated with a device identifier. The mobile device locationdata stored in the internal location database 350 and associated with adevice identifier may be accessed by the third-party applicationprovider 140 for generation of content customized to the location of themobile device 110.

For example, when a mobile device 110 requests 450 a service, such as anapplication or other content, from the third-party service provider 140,the third-party service provider 140 obtains location informationassociated with the mobile device 110 from the LBS platform server 130.The third-party service may be requested 450 by a mobile device usersubscribing to the third-party service provider 140 or installing anapplication from the third-party service provider 140. In oneembodiment, when the third-party service is requested, a mobile deviceuser provides a user identifier, such as a username or email address,allowing the third-party service provider 140 to uniquely identify themobile device user.

The third-party service provider 140 transmits 455 the publisheridentifier of the third-party service provider 140 and the useridentifier to the LBS platform server 130, which determines 460 thedevice identifier associated with the transmitted publisher identifierand user identifier. Using the device-provider association table 320 tocorrelate a device identifier with a provider identifier and useridentifier pair allows the third-party service provider 140 to obtainlocation data from the LBS platform server 130 without accessing themobile device 110. This increases the privacy of the mobile device 110.

After determining 460 the device identifier associated with the provideridentifier and user identifier from the device-provider associationtable 320, location data associated with the determined deviceidentifier is retrieved 465 from the internal location database 350. Thelocation data associated with the determined device identifier istransmitted 470 from the LBS platform server 130 to the third-partyservice provider 140. In an embodiment, the Third-party service server330 and/or the API generator 340 specifies the format in which thelocation data is transmitted 470 to the third-party service provider140. For example, the API generator 340 specifies when location data istransmitted from the LBS platform server 130 to a third-party serviceprovider 140.

After receiving the location data, the third-party service provider 140uses the location data to provide the requested service. For example,the third-party service provider 140 uses the location data to generatecontent, such as notifications, updates or coupons, associated with thedevice location. The third-party service is then transmitted 475 fromthe third-party service provider 140 to the mobile device 110. Variousformats, such as text messages, email messages, web page updates or anyother suitable format, may be used to transmit 475 the location data tothe third-party service provider 140. Hence, the LBS platform server 130and location data collection client 225 determine the geographiclocation of a mobile device 110, and the LBS platform server 130 allowsa third-party service provider 140 to access the geographic location ofthe mobile device 110 without directly accessing the mobile device 110.This enables the third-party service provider 140 to incorporategeographic location specific features into its services while preservingthe privacy of mobile device users by using the LBS platform server 130,rather than the mobile device 110, to disseminate location information.

FIG. 5 is a flow chart of one embodiment of method for a LBS platformserver 130 providing location information about a location of a mobiledevice 110. The actions described in FIG. 5 can be implemented by aprocessor executing instructions that cause the described actions. Thoseof skill in the art will recognize that one or more of the actions maybe implemented in embodiments of hardware and/or software orcombinations thereof. For example, instructions for performing thedescribed actions are embodied or stored within a computer readablestorage medium. Other embodiments can include different and/oradditional steps than the ones described here.

The LBS platform server 130 stores 505 a device identifier received froma mobile device 110 running the location data collection client 225 inthe device identifier store 305. The device identifier comprises acombination of a client identifier generated by the LBS platform server130 when the location data collection client 225 is installed or firstrun on the mobile device 110 and a mobile device identifier, such as anESN or IMEI number, extracted from the mobile device 110 by the locationdata collection client 225. The device identifier uniquely identifiesthe mobile device 110 running the location data collection client 225.To allow a third-party provider 140 to access stored location data, theLBS platform server generates 510 and stores a provider identifier,which uniquely identifies a third-party provider 140, in the provideridentifier store 310. The provider identifier is also transmitted fromthe LBS platform server 130 to the third-party service provider 140, sothat subsequent communications between LBS platform server andthird-party service provider include the provider identifier.

As the third-party service provider 140 allocates content, applicationsor other services on a per-user basis rather than a per-device basis,the third-party service provider 140 maintains user data, such as useridentifiers, such as login name, email addresses or any other identifierthat uniquely identifies a user. The user data and provider identifieris received 520 by the LBS platform server 130 to identify users of thethird-party service provider 140. However, the LBS platform server 130stores location information for different mobile devices 110 rather thanfor individual users. Accordingly, the device-provider association table320 maps 530 a stored device identifier to the received user data andprovider data. This allows the device-provider association table 320 toidentify a mobile device 110, using the device identifier, correspondingto a user of the third-party service 140.

When the LBS platform server 130 receives 540 a request from thethird-party service provider 140, including the provider identifier anduser data, for a location of a third-party service provider user, theLBS platform server determines 550 the device identifier associated withthe provider identifier and user data included in the request using thedevice-provider association table 320. Location data associated with thedetermined device identifier is then retrieved 560 from the internallocation database 350 and communicated to the third-party serviceprovider 140 according to an API included in the Third-party serviceserver 330 or the API generator 340.

Updating Mobile Device Location

FIG. 6 is a flow chart of an example method for updating data describingthe geographic location of a mobile device 110. The actions described inFIG. 6 can be implemented by a processor executing instructions thatcause the described actions. Those of skill in the art will recognizethat one or more of the actions may be implemented in embodiments ofhardware and/or software or combinations thereof. For example,instructions for performing the described actions are embodied or storedwithin a computer readable storage medium. Other embodiments can includedifferent and/or additional steps than the ones described here.

After initial installation and upon activation, a location datacollection client 225 extracts data from the mobile device 110, such aslatitude and longitude coordinates from a GPS module 270, a location APIon the mobile device 110 or identifiers associated with wireless accesspoints or cell towers accessed by a communication module 260. At least aportion of the extracted data may be used to identify or calculation thegeographic location of the mobile device 110. The extracted data istransmitted 605 from the mobile device 110 to a location based services(LBS) platform server 130 at a defined frequency, such as every fiveminutes. To conserve mobile device resources, such as allocatedbandwidth or power supply life, the transmission frequency may bemodified based on characteristics of the mobile device 110.

While the location data collection client 225 is running, the extracteddata is used to determine 610 whether the mobile device 110 isstationary. The mobile device 110 is determined 610 to be stationary ifthe location of the mobile device has not changed during the prior threetransmission periods. For example, if the mobile device 110 remains inthe same location for twenty minutes and the transmission frequency isfive minutes, the mobile device is considered to be stationary.

Responsive to determining 610 the mobile device 110 is stationary, thedata transmission frequency is decreased 650. For example, thetransmission frequency is decreased 650 so the extracted data istransmitted one hour later. The transmission frequency may be furtherdecreased 650 if the mobile device 110 remains stationary. For example,if the mobile device 110 is still stationary after an hour, theextracted data is transmitted again after two hours and if the mobiledevice 110 again remains stationary, the transmission frequency isfurther decreased 650 so the extracted data is transmitted at four hourintervals. However, when the extracted data changes, indicating that themobile device 110 has changed position, the transmission frequency isincreased to its original defined value.

Responsive to determining 610 the mobile device 110 is not stationary,the location data collection client 225 continues to transmit 620 dataaccording to the defined transmission frequency. The power of the mobiledevice 110 is also determined 630, and the data transmission frequencyis modified 640 according to the determined power, allowing the datatransmission frequency to be automatically decreased to conserve power.For example, if the mobile device power is determined 630 to be lessthan or equal to half of its full capacity, the data transmissionfrequency is decreased (e.g., data is transmitted at 10 minute intervalsrather than 5 minute intervals). This allows the location datacollection client 225 to modify data transmission to allow for accuratedetermination of current mobile device 110 location while efficientlyusing mobile device resources.

SUMMARY

The foregoing description of the embodiments of the invention has beenpresented for the purpose of illustration; it is not intended to beexhaustive or to limit the invention to the precise forms disclosed.Persons skilled in the relevant art can appreciate that manymodifications and variations are possible in light of the abovedisclosure.

Some portions of this description describe the embodiments of theinvention in terms of algorithms and symbolic representations ofoperations on information. These algorithmic descriptions andrepresentations are commonly used by those skilled in the dataprocessing arts to convey the substance of their work effectively toothers skilled in the art. These operations, while describedfunctionally, computationally, or logically, are understood to beimplemented by computer programs or equivalent electrical circuits,microcode, or the like. Furthermore, it has also proven convenient attimes, to refer to these arrangements of operations as modules, withoutloss of generality. The described operations and their associatedmodules may be embodied in software, firmware, hardware, or anycombinations thereof.

Any of the steps, operations, or processes described herein may beperformed or implemented with one or more hardware or software modules,alone or in combination with other devices. In one embodiment, asoftware module is implemented with a computer program productcomprising a computer-readable medium containing computer program code,which can be executed by a computer processor for performing any or allof the steps, operations, or processes described.

Embodiments of the invention may also relate to an apparatus forperforming the operations herein. This apparatus may be speciallyconstructed for the required purposes, and/or it may comprise ageneral-purpose computing device selectively activated or reconfiguredby a computer program stored in the computer. Such a computer programmay be stored in a tangible computer readable storage medium, whichinclude any type of tangible media suitable for storing electronicinstructions, and coupled to a computer system bus. Furthermore, anycomputing systems referred to in the specification may include a singleprocessor or may be architectures employing multiple processor designsfor increased computing capability.

Embodiments of the invention may also relate to a computer data signalembodied in a carrier wave, where the computer data signal includes anyembodiment of a computer program product or other data combinationdescribed herein. The computer data signal is a product that ispresented in a tangible medium or carrier wave and modulated orotherwise encoded in the carrier wave, which is tangible, andtransmitted according to any suitable transmission method.

Finally, the language used in the specification has been principallyselected for readability and instructional purposes, and it may not havebeen selected to delineate or circumscribe the inventive subject matter.It is therefore intended that the scope of the invention be limited notby this detailed description, but rather by any claims that issue on anapplication based hereon. Accordingly, the disclosure of the embodimentsof the invention is intended to be illustrative, but not limiting, ofthe scope of the invention, which is set forth in the following claims.

What is claimed is:
 1. A method for providing location-based services ata location-based services (LBS) platform server, the method comprising:receiving location data and a device identifier from a mobile deviceassociated with a user of a third-party service provider, the locationdata related to a current location of the mobile device; receiving aprovider identifier and user specific data from the third-party serviceprovider, the provider identifier uniquely identifying the third-partyservice provider, and the user-specific data uniquely identifying theuser of the third-party service provider; accessing a device-providerassociation table to map the received provider identifier and thereceived user-specific data to the device identifier of the mobiledevice associated with the user of the third-party service provider; andproviding location information to the third-party service provider, thelocation information describing a location of the mobile device.
 2. Themethod of claim 1, further comprising determining the locationinformation based on the location data received from the mobile device.3. The method of claim 2, wherein the location data received from themobile device comprises at least one of: latitude and longitudecoordinates for a current location of the mobile device; an identifierfor a wireless access point accessed by the mobile device; and anidentifier for a cell tower accessed by the mobile device; and whereinthe location information provided to the third-party service providerincludes at least one of a street address, a city, a zip code, and acountry.
 4. The method of claim 1, wherein the device-providerassociation table associates the device identifier with the provideridentifier, and further associates the device identifier with theuser-specific data.
 5. The method of claim 4, wherein thedevice-provider association table further associates the deviceidentifier with permissions specifying restrictions on the locationinformation that is provided to the third-party service provider.
 6. Themethod of claim 1, wherein providing location information to thethird-party service provider comprises: sending the location informationto the third-party service provider responsive to receiving the locationdata from the mobile device.
 7. The method of claim 1, wherein providinglocation information to the third-party service provider comprises:receiving one or more parameters from the third-party service provider,the parameters specifying one or more conditions relating to thelocation of the mobile device; and determining whether the locationinformation of the mobile device satisfies the received parameters; andsending the location information to the third-party service providerresponsive to determining that the received parameters have beensatisfied.
 8. The method of claim 7, wherein the received parameters aresatisfied when the location information indicates that the mobile deviceis within a predefined radius of an entity.
 9. The method of claim 7,wherein the received parameters are satisfied when the locationinformation changes at more than a predefined rate.
 10. The method ofclaim 1, further comprising: storing the location information in alocation database, the location information stored in association withthe device identifier, and wherein providing location information to thethird-party service provider comprises: receiving a request from thethird-party service provider for the location of the user of thethird-party service provider; and sending the location information tothe third-party service provider responsive to receiving the request.11. The method of claim 10, further comprising: identifying, to thethird-party service provider, other mobile devices within a specifiedradius of the location of the mobile device.
 12. The method of claim 10,further comprising: sending a timestamp to the third-party serviceprovider, the timestamp specifying when the location information wasdetermined.
 13. A location-based services (LBS) platform server, the LBSplatform server comprising: a location calculator configured todetermine location information of a mobile device in communication withthe LBS platform server using location data received from the mobiledevice; a device-provider association table configured to: receive, froma third-party service provider, a provider identifier uniquelyidentifying the third-party service provider and user-specific datauniquely identifying a user of the third-party service provider, and mapthe received provider identifier and the received user-specific data toa device identifier of a mobile device associated with the user of thethird-party service provider; and a third-party services serverconfigured to receive a device identifier from the device-providerassociation table and provide the location information of the mobiledevice associated with the received device identifier to the third-partyservice provider.
 14. The LBS platform server of claim 13, wherein thelocation information provided to the third-party service provider is thesame as the location data received from the mobile device associatedwith the user of the third-party service provider.
 15. The LBS platformof claim 13, wherein the location data received from the mobile devicecomprises at least one of: latitude and longitude coordinates for acurrent location of the mobile device, an identifier for a wirelessaccess point accessed by the mobile device, and an identifier for a celltower accessed by the mobile device, and wherein the locationinformation provided to the third-party service provider includes atleast one of a street address, a city, a zip code, and a country. 16.The LBS platform server of claim 13, wherein the device-providerassociation table associates each device identifier with a provideridentifier, and further associates each device identifier withuser-specific data.
 17. The LBS platform server of claim 13, wherein thedevice-provider association table further associates each deviceidentifier with permissions specifying restrictions on the locationinformation of the corresponding mobile device that is provided to thethird-party service provider.
 18. The LBS platform server of claim 13,wherein providing the determined location of the mobile device to thethird-party service provider comprises: sending the location informationto the third-party service provider responsive to determining thelocation information of the mobile device.
 19. The LBS platform serverof claim 13, wherein providing the determined data of the mobile deviceto the third-party service provider comprises: receiving one or moreparameters from the third-party service provider, the parametersspecifying one or more conditions relating to the location of the mobiledevice; and responsive to determining the location information of themobile device, determining whether the location information satisfiesthe received parameters; and sending the location information to thethird-party service provider responsive to determining that the receivedparameters have been satisfied.
 20. The LBS platform server of claim 13,further comprising: a location database containing the locationinformation determined by the location calculator for each mobiledevice, each determined location information associated with a deviceidentifier for the corresponding mobile device, wherein providing thedetermined location of the mobile device associated the received deviceidentifier to the third-party service provider comprises: receiving arequest for the location of the user of the third-party serviceprovider; responsive to receiving the request, retrieving, from thelocation database, the location information associated with the receiveddevice identifier; sending the retrieved location information to thethird-party service provider.